Systems, methods, and apparatus for external cardiac pacing

ABSTRACT

Systems and methods for cardiac pacing during a procedure are disclosed and may include an external pulse generator (EPG) for connecting to a lead. A remote-control module (RCM) wirelessly connected to the EPG may include user inputs to control the EPG. A central processing unit (CPU) with a memory unit for storing code and a processor for executing the code may be included where the CPU is connected to the EPG and RCM. The code may control the EPG in response to user input from the RCM. The CPU may be disposed in the EPG or the RCM, or an interface module (IM) configured to communicate between an otherwise conventional EPG and the RCM. The executable code may perform a continuity test (CT) routine, a capture check (CC) routine, rapid pacing (RP) routine, and/or a back-up pacing (BP) routine, in response to user input from the RCM.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of and claims the benefit of U.S.patent application Ser. No. 17/739,893, filed on May 9, 2022, whichclaims the benefit of U.S. Provisional Patent Application 63/230,064,filed Aug. 6, 2021, and U.S. Provisional Patent Application 63/268,498,filed Feb. 25, 2022, the entire contents of each of which areincorporated herein by reference.

FIELD

The present disclosure generally relates to external cardiac pacingdevices and methods.

BACKGROUND

External pulse generators are used in a variety of clinical applicationssuch as cardiac pacing in transcatheter heart valve (THV) replacementprocedures, most commonly in current clinical practice, transcatheteraortic valve replacement (TAVR). In this application, the heart may bebriefly paced at an elevated rate to reduce the cardiac flow, and thusthe pressure gradient, across the annulus where the artificial valve isto be deployed. In doing so, the propensity for an excessive pressuregradient to cause the artificial valve to move during deployment ismitigated, thus enabling accurate valve positioning and avoiding valveembolization. Currently, this is performed using an external pulsegenerator (EPG) to drive a temporary pacing wire positioned in theventricle, for example. A third person (e.g., surgical nurse ortechnician) outside the sterile field manually operates the pulsegenerator according to verbal instructions provided by the cardiologistwho is in the sterile field monitoring the patient and attending tovalve delivery and deployment. The use of a third party to manuallyoperate the EPG based on verbal instructions is susceptible to humanerror, both in communication and execution, potentially introducingunnecessary risk to the procedure.

SUMMARY

To mitigate such risk, the present disclosure describes systems andmethods for the cardiologist to directly control the pacing activity byplacing pacing control features in close proximity to the cardiologist,e.g., in the sterile field, thus eliminating the need for a third personand the need for verbal commands. In addition, the present disclosuredescribes systems and methods that have a level of automation, replacingsome of the manual control of the external pulse generator withautomatic algorithms.

One example embodiment provides a system for assisted pacing during acardiac procedure such as a TAVR procedure. The system may include anexternal pulse generator (EPG) configured for connection to a lead suchas a guidewire. The system may also include a remote-control module(RCM) wirelessly connected to the EPG, wherein the RCM includes userinputs configured to control the EPG. To facilitate connection to aguidewire with at least a partial insulative outer portion, the systemmay include a guidewire connector configured to penetrate the insulativeouter portion to establish electrical communication with the guidewire.The system may include a central processing unit (CPU) with a memoryunit for storing code and a processor for executing the code, whereinthe CPU is operably connected to the EPG and RCM. The code may includeinstructions to assist in control of the EPG based on user input fromthe RCM. The CPU may be disposed in the EPG or the RCM, or an interfacemodule (IM) configured to communicate between an otherwise conventionalEPG and the RCM.

The code may include instructions to perform a continuity test (CT)routine, a capture check (CC) routine, rapid pacing (RP) routine, and/ora back-up pacing (BP) routine, all based on user input from the RCM.

The CC routine may include the steps of waiting for a user readinessinput from the RCM, ramping up a paced pulse rate (PPR) from the EPG,determining if a sensed heart-rate (HR) is the same as the PPR, andtriggering an indicator indicative of 1:1 capture. The CC routine mayfurther include an automatic rate determination and ramp-up subroutine.The CC routine may further include a manual capture rate determinationand ramp-up or ramp-down subroutine. The CC routine may further includea capture verification subroutine. The capture verification subroutinemay monitor PPR and/or HR over a period corresponding to at least onerespiratory cycle.

The RP routine may include the steps of waiting for a user readinessinput from the RCM, ramping up a pacing output from the EPG, andtriggering an indicator when the PPR or HR is suitable for valvedeployment. The RP routine may further include an automatic ramp upsubroutine and an automatic ramp down subroutine. The amplitude of thepacing output may be higher in the RP routine than the amplitude in theCC routine.

The BP routine may include the steps of waiting for a user readinessinput from the RCM, ramping down the PPR from the EPG, determining if aHR is inhibited due to the detection of an intrinsic heart beat prior tothe pace pulse would otherwise be delivered (in VVI mode), andtriggering an indicator indicative of inhibition. In the presence ofintrinsic abnormal bradycardia from heart block or other pathologicalcauses, the EPG may ramp up PPR to a normal HR to stabilize thepatient's hemodynamics.

Another example embodiment provides a method for assisted pacing duringa cardiac procedure such as a TAVR procedure. The method may include thesteps of connecting an external pulse generator (EPG) to a lead orguidewire, connecting a remote-control module (RCM) to the EPG via awireless connection, activating a computer executable code based on auser input from the RCM, and executing code instructions to performassisted pacing based on user input from the RCM. Executing theinstructions may include steps to perform a continuity test (CT)routine, a capture check (CC) routine, rapid pacing (RP) routine, and/ora back-up pacing (BP) routine, all based on user input from the RCM, asdescribed above.

Another example embodiment disclosed herein provides a system forcardiac pacing. The system may include an EPG configured to connect to alead and to provide pacing outputs; an RCM may be wirelessly connectedto the EPG, wherein the RCM may be configured to receive user inputs andto control the EPG; and a CPU that may be operably connected to the EPGand RCM, the CPU may be configured to execute code, wherein the code mayinclude instructions to perform a (RP routine in response to a firstuser input received at the RCM, the RP routine may include: receiving auser readiness input from the RCM; modifying a PPR of a pacing outputfrom the EPG in response to the user readiness input; determining if themodified PPR meets a predetermined setting; and triggering an indicatorif the modified PPR meets the predetermined setting.

Aspects of the disclosed system for cardiac pacing may include one ormore of the following features: the RP routine may further include anautomatic PPR ramp up subroutine; the code may further includeinstructions to perform a CT routine, the CT routine may include:determining that the lead is connected to the EPG and triggering anindicator in response to determining that the lead is connected to theEPG; disabling one or more accessory buttons in response to determiningthat the lead is connected to the EPG; the code may further includeinstructions to perform a CC routine in response to a second user inputreceived at the RCM, the CC routine may include: receiving the userreadiness input from the RCM, ramping up the PPR of the pacing outputfrom the EPG to a ramped up PPR in response to receiving the userreadiness input, determining if a sensed heart-rate (HR) isapproximately the same as the ramped up PPR, and triggering an indicatorindicative of a 1:1 capture in response to determining if the sensed HRis approximately the same as the ramped up PPR of the pacing output; theCC routine may further include an automatic rate determinationsubroutine; the CC routine may further include at least one of a manualcapture rate determination subroutine or a capture verificationsubroutine; the capture verification subroutine may monitor capture overa period of at least one respiratory cycle; the code may further includeinstructions to perform a BP routine in response to a second user inputreceived at the RCM, the BP routine may include: receiving the userreadiness input from the RCM, ramping down the PPR from the EPG inresponse to receiving the user readiness input, determining if aheart-rate (HR) is inhibited, and triggering an indicator indicative ofinhibition in response to determining if the HR is inhibited; the EPGmay be a non-sterile component and the RCM may be a sterile component;the EPG may be configured to transmit pacing output information to a labdisplay; the EPG may be configured to operate in either unipolar orbipolar modes of operation; the EPG may be further configured forconnection to a grounding pad; the EPG may be configured to receivesensing signals from the lead; the EPG may be configured to receive anelectrocardiogram (ECG) signal; the lead may include a guidewire with atleast a partial insulative outer portion; a guidewire connector may beconnected to the EPG via a cable, wherein the guidewire connector may beconfigured to penetrate the partial insulative outer portion toestablish electrical communication with the guidewire; the CPU may bedisposed in the EPG or the RCM; an interface module (IM) may facilitatecommunication between the EPG and RCM; and the CPU may be disposed inthe IM.

Another example embodiment disclosed herein provides a method of cardiactreatment (e.g., pacing). The method may include connecting an EPG to aguidewire; connecting an RCM to the EPG; executing first codeinstructions to perform an RP routine to modify a PPR of a pacing outputfrom the EPG in response to a first user input from the RCM; andtriggering an indicator when the PPR reaches a predetermined setting forvalve deployment.

Aspects of the disclosed method may include one or more of the followingfeatures: the RP routine may include receiving a user readiness inputfrom the RCM; modifying a PPR of a pacing output from the EPG inresponse to the user readiness input; and determining if the PPR meetsthe predetermined setting for valve deployment based on modifying thePPR; deploying a valve in response to determining if the PPR meets thesetting for valve deployment; executing second code instructions toperform a CT routine, where the CT routine may include: determining thatthe guidewire is connected to the EPG and triggering an indicator inresponse to determining that the guidewire is connected to the EPG;executing second code instructions to perform a CC routine in responseto a second user input from the RCM, where the CC routine may furtherinclude: receiving a user readiness input from the RCM, ramping up thePPR of the pacing output from the EPG to a ramped up PPR, determining ifa sensed heart-rate (HR) is approximately the same as the ramped up PPR,and triggering an indicator indicative of a 1:1 capture in response todetermining if the sensed HR is approximately the same as the ramped upPPR of the pacing output; and executing second code instructions toperform a BP routine in response to a second user input from the RCM,where the BP routine may include: receiving a user readiness input fromthe RCM, ramping down the PPR from the EPG in response to the userreadiness input, determining if a heart-rate (HR) is inhibited, andtriggering an indicator indicative of inhibition in response todetermining if the HR is inhibited.

Another example embodiment disclosed herein includes a system forcardiac pacing. The system may include an EPG configured to connect to alead and to provide pacing outputs; an RCM operably connected to theEPG, wherein the RCM is configured to receive user inputs and to controlthe EPG in response to the user inputs; and a processor in communicationwith the EPG and RCM, the processor configured to transmit signals tothe EPG to perform at least one of RP routine, a CT routine, a CCroutine, or a BP routine.

Aspects of the disclosed system for cardiac pacing may include one ormore of the following features: the RP routine may include: receiving auser readiness input from the RCM, modifying a PPR of a pacing outputfrom the EPG in response to receiving the user readiness input,determining if the modified PPR meets a setting for valve deployment,and triggering an indicator if the PPR meets the setting for valvedeployment; the CT routine may include: determining that the lead isconnected to the EPG and triggering an indicator in response todetermining that the lead is connected to the EPG; the CC routine mayinclude: receiving a user readiness input from the RCM, ramping up a PPRof the pacing output from the EPG to a ramped up PPR in response toreceiving the user readiness input, determining if a sensed heart-rate(HR) is approximately the same as the ramped up PPR, and triggering anindicator indicative of a 1:1 capture in response to determining if thesensed HR is approximately the same as the ramped up PPR of the pacingoutput; and the BP routine may include: receiving a user readiness inputfrom the RCM, ramping down a PPR from the EPG in response to receivingthe user readiness input, determining if a heart-rate (HR) is inhibited,and triggering an indicator indicative of inhibition in response todetermining if the HR is inhibited.

The above summary is not intended to describe each and every embodimentor implementation of the present disclosure.

BRIEF DESCRIPTION OF THE FIGURES

The accompanying drawings, which are incorporated into and constitute apart of this specification, illustrate various exemplary embodimentsand, together with the description, serve to explain the principles ofthe disclosed embodiments. The drawings show different aspects of thepresent disclosure and, where appropriate, reference numeralsillustrating like structures, components, materials, and/or elements indifferent figures are labeled similarly. It is understood that variouscombinations of the structures, components, and/or elements, other thanthose specifically shown, are contemplated and are within the scope ofthe present disclosure.

There are many inventions described and illustrated herein. Thedescribed inventions are neither limited to any single aspect norembodiment thereof, nor to any combinations and/or permutations of suchaspects and/or embodiments. Moreover, each of the aspects of thedescribed inventions, and/or embodiments thereof, may be employed aloneor in combination with one or more of the other aspects of the describedinventions and/or embodiments thereof. For the sake of brevity, certainpermutations and combinations are not discussed and/or illustratedseparately herein. Notably, an embodiment or implementation describedherein as “exemplary” is not to be construed as preferred oradvantageous, for example, over other embodiments or implementations;rather, it is intended reflect or indicate the embodiment(s) is/are“example” embodiment(s).

The drawings illustrate example embodiments of the present disclosureand, along with the description, serve to explain the principles of thedisclosure. The drawings are only illustrative of certain embodimentsand do not limit the disclosure or invention.

FIG. 1A is a schematic block diagram of a pacing assist system for usein a cardiac procedure such as TAVR, according to an example embodimentof the present disclosure;

FIG. 1B is a schematic block diagram of a pacing assist system,according to an alternative example embodiment of the presentdisclosure;

FIG. 1C is a schematic block diagram of a pacing assist system,according to another alternative example embodiment of the presentdisclosure;

FIG. 2 is a schematic illustration from a user's perspective of thepacing assist system shown in FIG. 1A, according to an exampleembodiment of the present disclosure;

FIGS. 3A and 3B are schematic illustrations of an alternativeremote-control module for use in the system shown in FIG. 2 ;

FIGS. 4A and 4B are schematic illustration of a guidewire connectorshown in perspective and side views, respectively, according to anexample embodiment of the present disclosure;

FIG. 5 is a schematic flow chart of example operational stages for usein the systems shown in FIGS. 1A, 1B and 1C, according to an embodimentof the present disclosure;

FIG. 6 is a schematic flow chart showing an example overview of thecapture check process as generally described with reference to FIG. 5 ;

FIG. 7 is a schematic flow chart showing an example overview of therapid pacing process as generally described with reference to FIG. 5 ;and

FIGS. 8, 9, 10A, 10B, 11A, 11B, 11C, 11D, 12A, 12B, and 13 are schematicflow charts showing detailed examples of the processes generallydescribed with reference to FIG. 5 .

While embodiments of the disclosure are amenable to variousmodifications and alternative forms, specifics thereof have been shownby way of example in the drawings and will be described in some detail.It should be understood, however, that the intention is not to limit thedisclosure to the particular embodiments described. On the contrary, theintention is to cover all modifications, equivalents, and alternativesfalling within the spirit and scope of the invention.

As used herein, the terms “comprises,” “comprising,” “includes,”“including,” or any other variation thereof, are intended to cover anon-exclusive inclusion, such that a process, method, article, orapparatus that comprises a list of elements does not include only thoseelements, but may include other elements not expressly listed orinherent to such process, method, article, or apparatus. The term“exemplary” is used in the sense of “example,” rather than “ideal.” Inaddition, the terms “first,” “second,” and the like, herein do notdenote any order, quantity, or importance, but rather are used todistinguish an element or a structure from another. Moreover, the terms“a” and “an” herein do not denote a limitation of quantity, but ratherdenote the presence of one or more of the referenced items.

The term “distal end,” or any variation thereof, refers to the portionof a device farthest from an operator of the device during a procedure.Conversely, the term “proximal end,” or any variation thereof, refers tothe portion of the device closest to the operator of the device.Further, any use of the terms “around,” “about,” “substantially,” and“approximately” generally mean+/−10% of the indicated value.

DETAILED DESCRIPTION

FIG. 1A is a schematic block diagram of a pacing assist system 100A foruse in a TAVR procedure, for example, according to an example embodimentof the present disclosure. System 100A may generally include an externalpulse generator 200 configured for connection to a lead 20 via a cable.External pulse generator 200 may be a temporary or single-use pulsegenerator. Lead 20 may be positioned with its proximal end extending outfrom the access sheath and its distal end in the heart 10 (e.g., left orright ventricle) to establish electrical communication between the EPG200 and the heart 10. The connection between the EPG 200 and lead 20 maybe bidirectional to facilitate pacing and EGM (intracardiacelectrocardiogram) sensing.

System 100A may also generally include a remote-control module (RCM) 300connected to the EPG 200 and configured to control pacing output fromthe EPG 200 based on user input from the cardiologist. RCM 300 may beconnected to the EPG 200 via a wireless connection (e.g., Bluetooth) ora hard wired connection (e.g., extended cable). The connection betweenthe RCM 300 and the EPG 200 may also be bidirectional such that the RCM300 may issue command signals to the EPG 200, and the EPG 200 may issuestatus signals to the RCM 300. In use, the EPG 200 may be placed outsidethe sterile field, whereas the RCM 300 may be placed proximate the handsof the cardiologist inside the sterile field.

Lead 20 may be unipolar or bipolar. If unipolar, EPG 200 may also beconfigured for connection to a grounding pad (not shown). Lead 20 maycomprise a conventional guidewire that is unipolar or a specialtytemporary pacing guidewire (e.g., Wattson®, Teleflex, Inc.) that isbipolar. Those of ordinary skill will also recognize that any suitablelead may be used in conjunction with the principles of the presentdisclosure. If a conventional guidewire is used for lead 20, a guidewireconnector (not shown) may be provided to facilitate an electricalconnection thereto. Because conventional guidewires often have aninsulative outer surface (e.g., Teflon® coating), the guidewireconnector may be configured to penetrate the insulation to achieve anelectrical connection to the metal (e.g., 304 v stainless steel) portionof the guidewire.

Output from the EPG 200 may be connected to a conventional lab display30 (such as the C-View® Large Display from Carrot Medical). Examples ofinformation shown on display 30 may include static and/or cine views ofthe heart, intracardiac EGM, ECG, heart rate, respiratory rate and otherphysiologic or hemodynamic data. Additionally, a complete or partialmirror representation of the display information on the EPG 200 and/orRCM 300 may be shown on the display 30. For example, pacing waveform,pulse rate, pulse amplitude, pulse width and other pacing data, stageindicators, status and readiness indicators, procedural notes andinstructions, etc.

FIG. 1B is a schematic block diagram of an alternative pacing assistsystem 100B according to an alternative example embodiment of thepresent disclosure. In this embodiment, a conventional EPG 40 may beemployed. To facilitate connection and control between the conventionalEPG 40 and the RCM 300, an interface module (IM) 400 be used. The IM 400may be connected to the IPG 40 by hard wire, for example, and resideoutside the sterile field. The IM 400 may be wirelessly connected to theRCM 300 residing inside the sterile field adjacent the cardiologist'shands. The IM 400 may be configured to function in the same or similarmanner as EPG 200, absent the pulse engine and associated pacingoutputs. In other words, the IM 400 assumes command and control of theconventional EPG 40: the IM 400 becomes the master; and the conventionalEPG 40 becomes the slave. The connections between the RCM 300, IM 400and EPG 40 may be bidirectional such that the RCM 300 may issue commandsignals to the IM 400 which are translated to the EPG 40. Similarly, theEPG 40 may issue status signals to the IM 400 which are translated tothe RCM 300.

FIG. 1C is a schematic block diagram of an alternative pacing assistsystem 100C according to an alternative example embodiment of thepresent disclosure. In this embodiment, an alternative EPG 250configuration may be employed, wherein the EPG may include a smartdevice 254 and a pulse generator/sensing circuit 256. The smart device254 may comprise a conventional smart phone, tablet, etc., for example,which typically contain input/output (I/O), display, wirelesscommunication, power, processor and memory features. When combined witha pulse engine and sensing circuit 256, EPG 250 may be configured tohave the same functionality as EPG 200 and may be operated in a similarfashion. The EPG 250 may reside outside the sterile field, for example,and may be directly connected to the lead 20 via pulse and sensingcircuit 256, directly connected to the lab display 30 via smart device254, and wirelessly connected to the RCM 300 via smart device 254.

As will be described in more detail herein, systems 100A, 100B, and 100Cmay incorporate a central processing unit (CPU) with a memory unit forstoring code and a processor for executing the code. The CPU may beoperably connected to the RCM 300 and the EPG 200 in system 100A, to theRCM 300 and IM 400 in system 100B, or the RCM 300 and the smart device254 in EPG 250 in system 100C. The CPU may be disposed in the EPG 200,the EPG 250, the RCM 300, or the IM 400. According to an embodiment, theCPU may be a cloud component operably connected to the RCM 300 and/orEPG 200 via a network connection. In this embodiment, the CPU mayreceive data from EPG 200 and/or RCM 300 and may transmit signals to EPG200 and/or RCM 300 (e.g., over the network connection). The executablecode may include instructions to control the EPG 200, 250, or 40 basedon user input from the RCM 300. As used hereinafter, systems 100A, 100B,and 100C may be referred to collectively as system 100.

FIG. 2 is a schematic illustration from a user's perspective of thepacing assist system 100A shown in FIG. 1A, according to an exampleembodiment of the present disclosure. In this example embodiment, theheart 10 may be paced via a guidewire 20 placed in the left ventricle(LV), for example. A valve delivery system (not shown) may be deliveredover the guidewire 20 to the desired location for valve deployment. Ingeneral, the pacing signal output from EPG 200 may be electricallyconnected to the guidewire 20 by way of a cable 52 and a guidewireconnector clamp 50. As mentioned previously, the guidewire connector 50may be configured to penetrate insulation on the guidewire 20 to achievean electrical connection to the conductive (e.g., metal) portion of theguidewire 20. In this manner, the EPG 200 may be electrically coupled tointracardiac tissue of the heart 10 for purposes of pacing and sensing(EGM).

Also as mentioned previously, a bipolar guidewire 20 may be used forbipolar pacing. Examples of bipolar configurations are described in U.S.Pat. Nos. 10,173,052; 10,758,725; 10,881,851; and 11,045,318, the entiredisclosures of which are incorporated herein by reference.Alternatively, a conventional guidewire 20 may be used for unipolarpacing, together with a grounding pad 60, also electrically connected tothe EPG 200 via a cable 62. Examples of unipolar configurations aredescribe in U.S. Published Patent Applications Nos. 2019/0224011,2021/0030440, and 2021/0186696, the entire disclosures of which areincorporated herein by reference.

The EPG 200 may include a number of input and output terminals (notvisible) mounted to the outside of the housing 202, including pacingoutput terminals (anode and cathode) for connection to the guidewire 20.The pacing output terminals may also serve as sensing input terminalsfor sensing EGM, and/or the EPG 200 may include a separate inputterminal(s) to receive an electrocardiogram (ECG). In either case, theEGM and ECG may be used to derive a cardiac wave form indicative of HRand other physiological parameters of cardiac function. The EPG 200 mayalso include and a ground terminal for connection to the grounding pad60 via cable 62.

The EPG 200 may include a number of user inputs on the front of thehousing 202, such as a power button 204, a primary button 206, anaccessory button 208, up 210 and down 212 buttons, a settings button214. Alternatively, or additionally, the EPG 200 may also be configuredto receive user inputs via a foot actuator, a voice actuation component,or any combination of user inputs discussed herein. In addition tocommand-and-control inputs from the user, the EPG may be configured toreceive and store settings such as patient-specific settings orphysician-specific preferences for pacing parameters, rate limits, etc.The EPG 200 may further include a number of stage and status indicatorssuch as indicators corresponding to a continuity test (CT) stage 220, acapture check (CC) stage 222, a rapid pacing (RP) stage 224, and aback-up pacing (BP) stage 226, for example. The status of each stage maybe represented by illuminating a different color. For example, thevarious states (e.g., pre-, performing, complete, failed) may berepresented by intuitive colors (e.g., white, yellow, green, red,respectfully) as shown in table 228.

The EPG 200 may be operated in different modes depending on what type ofTAVR valve is being deployed (e.g., self-expanding or balloonexpandable) and what type of pacing is being utilized (e.g., unipolar orbipolar). Bipolar pacing may be performed in the right ventricle using abipolar transvenous lead or in the left ventricle using a bipolarguidewire (e.g., Wattson Wire). Unipolar pacing may be performed in theright ventricle using a unipolar transvenous lead and a grounding pad orin the left ventricle using a conventional guidewire and a groundingpad. The grounding pad may alternatively comprise a ground electrodeattached to the access sheath or a ground electrode attached the chest.

In this example, the EPG 200 may be operated in four different modes:bipolar pacing for a balloon expandable valve mode; bipolar pacing for aself-expandable valve mode; unipolar pacing for a balloon-expandablevalve mode; and unipolar pacing for a self-expandable valve mode. Thedesired mode may be selected by the cardiologist using user inputs onthe EPG 200 or RCM 300, or at least partially automatically selected bydetecting what type of lead 20 (unipolar or bipolar) is connected to theEPG 200. Alternatively, the RCM 300 may be configured for a singlespecific mode, wherein different models may be available for the desiredmode. In either case, the mode of operation may be displayed by modeindicator 230.

The EPG 200 may, by way of example, not limitation, include otherindicators such as pace rate 232, pairing status 234, heart rate (notshown), blood pressure (not shown), respiratory rate (not shown), otherphysiological indicators (not shown), and a display screen 236 fordisplaying a wide variety of selectable information such asinstructions, procedural status, cardiac traces, physiologicinformation, etc. Pairing status indicator 234 may also be configured asa button, wherein short pressing (clicking) the button initiates pairingwith RCM 300 and long pressing the button disables pairing and clearspairing memory. Additionally, the EPG 200 may have a display outputconnected to the lab monitor 30 to display a complete or partial mirrorrepresentation of the indicator information on the EPG 200 and/or RCM300, in addition to static and/or cine views of the heart, intracardiacEGM, ECG, heart rate, respiratory rate and other physiologic orhemodynamic data. The EPG 200 may include different forms of indicatorssuch as audio, visual and tactile indicators.

The housing 202 of the EPG 200 may contain (not visible) typicalelectrical components for a conventional EPG such as, for example, apower source (e.g., primary cell), a power control unit (e.g., forconnection to an external power source), an output control module, aninput control module, a pulse engine, a sensing module, a signalprocessing module, an indicator control module (e.g., audio, visual,tactile, display), etc., all of which may be configured to functionaccording to the methods described herein. The EPG 200 may furtherinclude a communication module (e.g., two-way wireless) forcommunication with RCM 300, and a control module that includes a CPUwith a memory unit for storing code and a processor for executing thecode according to the methods described herein.

The RCM 300 may include a number of user inputs on the front of thehousing 302, such as a primary button 306, an accessory button 308, anup button 310 and down button 312, each corresponding to the samebuttons on EPG 200 with the same function. Each of the buttons may beback-lit to indicate status (lit=enabled/active;unlit=disabled/inactive). Note that the flowcharts may use “on” and“off” as shorthand for “active” and “inactive”, respectfully. Inaddition, each button may distinguish between a short press (referred toherein as “click”) and a long press (referred to herein as “press”),corresponding to different commands. The RCM 300 may also be equippedwith tactile (e.g., haptic) and audio (tone) indicators to indicatestatus such as alerts or readiness. The housing 302 of the RCM 300 maycontain (not visible) a power source (e.g., primary cell), acommunication module (e.g., two-way wireless) for communication with EPG200, and a control module, each of which may be configured to functionaccording to the methods described herein. The RCM 300 may be wirelesslyconnected to the EPG 200 via a Bluetooth protocol, for example. Thewireless connection between the EPG 200 and RCM 300 may provide forbidirectional exchange of information and commands.

The RCM 300 may have a form factor or shape as shown in FIG. 2 that isconfigured to rest on the operating table in the sterile field proximatethe cardiologist operating the TAVR system, with optional attachmentmeans for securement to sterile drapes or the like. Alternatively, theRCM 300 may be configured for attachment to the handle of the valvedelivery device. For example, as shown in FIGS. 3A and 3B, the housing302 may be configured to conform to and connect to the handle 70 of thevalve delivery device. The underside of the housing 302 may be concaveand include a mechanism for attachment to the handle of the valvedelivery device such as, for example, a mechanical interlock or anadhesive strip. In FIG. 3A, a balloon-expandable inflation device 70 isshown, which acts as a handle that the cardiologist holds to facilitatedelivery and deployment of the valve by balloon inflation.Alternatively, a self-expandable valve may be used with a correspondinghandle for delivery and deployment of the valve by self-expansion. Ineither case, the RCM 300 may be disposed on the handle such that thecardiologist may simultaneously operate the RCM 300 and control thevalve delivery system.

As mentioned elsewhere herein, if a conventional guidewire is used forlead 20 in a unipolar pacing configuration, a guidewire connector 50 maybe used to connect the guidewire to the EPG 200 via cable 52. An exampleembodiment of a guidewire connector 50 is shown in perspective view andside view in FIGS. 4A and 4B, respectively. In this example embodiment,the guidewire connector 50 may comprise a clip with one or two sets ofopposing arms 54. The arms 54 may be spring loaded and biased to aclosed position to grip the guidewire 20 unless manually opened by theuser. Each of the sets of arms 54 may include an upper arm 54A and alower arm 54B, with corresponding conductive and opposing terminals 56Aand 56B, respectively. The conductive terminals 56A and 56B may includeone or more sharp edges configured to penetrate insulation on theguidewire 20 to achieve an electrical connection to the metal portionthereof. Additionally, the conductive terminals 56A and 56B may includean irregular geometry for gripping the guidewire 20. The irregulargeometry may comprise, for example, a convex surface or protrusion and acorresponding concave surface or recess, which may be aligned or offsetto enhance grip.

The system 100 may be operated in four different stages, for example.The stages may be executed based on inputs from the RCM 300 and/or theEPG 200. Execution of these stages may be assisted by automation, forexample by instructions contained in the code stored in the memory ofthe CPU and executed by the processor as described previously. Suchinstructions and the associated methods may be explained by the variousstages schematically illustrated in FIG. 5 . Such stages may be executedalone or in combination, and the sequence of execution may be as shown,by way of example, not limitation.

As seen in FIG. 5 , which schematically illustrates an overview of theoperational stages, operation of the system 100 may start 590 with acontinuity test 600. Basically, the continuity test (CT) 600 determines602 if there is a non-intermittent electrical connection between the EPG200 and the lead 20, including the guidewire connector 50 and cable 52.CT 600 may be initiated automatically upon connecting EPG 200 and lead20 (e.g., based on a sensed connection, a connection based trigger, uponinitiating EPG 200, or the like) or may be selectively initiated inresponse to user input. If no continuity is found, then the operator maycheck and fix 604 such connections as appropriate, after which thecontinuity test 600 may be repeated. Note that the continuity test 600may be periodically repeated throughout the operation of the system 100,except during portions where it may interfere with the stage ofoperation in progress, such as a portion of the capture check.Continuity may be determined by applying an extremely small current tothe lead, in accordance with ISO60601-1, and measuring the resultingvoltage. Once continuity is found, the operation may move to the nextstage.

The next stage may be a capture check (CC) 700 which determines 702 if1:1 capture can be established, i.e., if the HR corresponds 1:1 withPPR. Lack of 1:1 capture may be due to the lead 20 not being in adequatecontact with (pace-able) intracardiac tissue. Lack of 1:1 capture mayalso occur due to premature ventricular contraction (PVC), wherein theheart contracts before responding to a pacing signal. Such lack of 1:1capture may be adjudicated and adjusted 704, e.g., by the cardiologist.Depending on the cause, such adjustments may include, for example,changing the position of the lead 20 to establish better contact withintracardiac tissue, ramping the PPR up and/or down, etc. Onceadjudicated and adjusted 704, the capture check 700 may be repeated, andonce 1:1 capture is confirmed 702, the operation may move to the nextstage.

The next stage may be rapid pacing (RP) 800 which determines 802 if thepacing conditions (e.g., PPR) and heart status (e.g., HR) areappropriate for valve deployment. Generally speaking, at a sufficientlyhigh paced HR, the stroke volume goes down to reduce the pressuregradient across the native valve annulus to mitigate valve embolizationduring deployment of a balloon expandable valve or to increase stabilityduring deployment of a self-expanding valve. During RP 800, the PPR of apacing output maybe modified (e.g., increased or decreased) in responseto receiving a user readiness input. According to an embodiment, theindicator may be triggered based on when the PPR and/or HR meet(s) aprovided or selected setting (e.g., provided by a healthcare provider).The indicator may be triggered when the PPR and/or HR meet(s) the userprovided or selected setting. If it is determined 802 that theconditions are satisfied (e.g., if the PPR and/or HR meet(s) a setting),the valve may be deployed 1000 by the cardiologist. However, if it isdetermined 802 that the conditions are not satisfied, the cause may beadjudicated and adjusted 804, e.g., by the cardiologist, after which therapid pacing stage 800 may be repeated. An example of where conditionsare not satisfied is lack of 1:1 capture due to heart block, wherein thePPR is faster than the heart is able to respond. In such a case, the PPRmay be greater than the HR, for example 2:1. Alternatively, failure toachieve the appropriate conditions may require a repeat of CT 600, CC700, and/or back-up pacing (BP) 900.

Once the valve is deployed 1000, the operation may enter a BP stage 900.Generally, the BP stage 900 may be used to return the heart 10 to itsintrinsic HR from the elevated PPR used for valve deployment. This maybe accomplished by reducing the PPR until HR>PPR wherein the pace signalis inhibited in VVI mode (pace ventricle, sense ventricle, inhibit ifintrinsic). VVI is standard pacing nomenclature in which the firstletter is the chamber paced, the second letter is the chamber sensed andthe third letter is the response to a sensed beat. In this case, theventricle is paced, the ventricle is also sensed, and if a beat issensed it inhibits the next pacing spike. This helps prevent the “R onT” phenomenon in which a pacer activates in the repolarization phase ofthe heart beat which can cause ventricular fibrillation and suddendeath.

FIG. 6 , which is a schematic flow diagram, provides more detail on theCC stage 700, by way of example, not limitation. The CC stage 700 starts696 with the cardiologist positioning 698 the lead 20 in the desiredposition for pacing. A confirmatory CT may be performed, whereincontinuity is determined 602. If continuity is not found 602, then theconnections of the lead 20 to the EPG 200 may be checked and fixed 604,and the lead position reestablished 698. If continuity is found, the EGMsignal may be sensed 708. If EGM is not detected, the lead position maybe repositioned 697 to receive a better signal. If EGM is detected, theEPG 200 may begin ramping up the pacing signal 710, wherein the PPR maybegin empirically around 80 to 120 pulses per minute (i.e., beats perminute (BPM)), ramping up at a rate of 5 to 15 pulses per minute every 1to 5 seconds, for example, wherein the PPR is not to exceed around 130to 160 pulses per minute by the automatic algorithm. Alternatively, theinitial PPR may begin at a rate calculated by measuring HR and adding 50BPM, for example. If needed, the operator may manually raise the HR upto a maximum of 200 pulses per minute using 310. By way of example, notnecessarily limitation, the pacing signal may be set to a pulseamplitude of approximately 1 to approximately 7 mA, and a pulse width ofapproximately 80 to approximately 140 ms, and preferably a pulseamplitude of approximately 7 mA and a pulse width of approximately 140ms, in VVI mode. While ramping up the PPR, a 1:1 capture check may beconfirmed 702. If it is determined 702 that 1:1 capture has not beenestablished, it may then be determined 714 if the lead is in contactwith pace-able tissue. If the lead is not in contact with pace-abletissue, the lead may be repositioned 697 and the loop may repeat. If itis determined that the lead is in contact with pace-able tissue, thepace rate may be ramped up 710 until 1:1 capture is established. When itis determined 702 that 1:1 capture has been initially established,capture may be confirmed over at least one respiratory cycle 712 (e.g.,around 6 to 10 seconds) to be certain capture can be maintainedindependent of heart movement due to respiration. Once capture isconfirmed for at least one respiratory cycle, the PPR may be ramped downto approximately 50 BPM, for example, a rate of approximately 5 toapproximately 15 BPM for approximately 5 to approximately 15 seconds,for example, wherein the PPR does not fall below around 30 to 50 pulsesper minute. The PPR may be ramped down until it is determined 904 thatpacing is inhibited (i.e., until HR>PPR meaning intrinsic pacing takesover). The steps of ramping down PPR 902 and determining if pacing isinhibited 904 are similar to the basic steps of back-up pacing 900. Oncecapture check 700 is complete, the operation may move to the next stage(e.g., RP stage 800).

Pacing parameters for CC may be different (lower in amplitude/pulsewidth) than the pacing parameters used during RP to provide safetymargin. I.e., finding the best location for pace-able tissue at a lowerpace amplitude will be a smaller zone. Should the lead move a littleduring RP, the higher pacing amplitude will help overcome the change andensure capture is maintained.

FIG. 7 , which is a schematic flow diagram, provides more detail on theRP stage 800, by way of example, not limitation. The RP stage 800 starts796 with the cardiologist positioning 798 the valve in the desiredposition prior to deployment, e.g., proximate the valve annulus. The EPG200 may send a pacing signal, ramping from around 140 to around 200pulses per minute above the sensed HR, ramping up at a rate ofapproximately 10 to approximately 20 pulses per minute everyapproximately 0.5 to approximately 2 seconds, for example. By way ofexample, not necessarily limitation, the pacing signal may be set to apulse amplitude of approximately 10 to approximately 25 mA, and a pulsewidth of approximately 80 to approximately 140 ms, or preferably a pulseamplitude of approximately 25 mA and a pulse width of approximately 140ms, in VVI mode. While ramping up the PPR, 1:1 capture may be confirmed702, and if 1:1 capture is lost at any time before valve deployment1000, the pacing signal may be ramped down 902 until it is determined904 that pacing is inhibited. While ramping up the PPR, heart block mayalso occur if the PPR exceeds the capability of the heart. Should thatoccur, PPR may be reduced gradually until capture is reestablished. If1:1 capture is maintained, the PPR may be ramped until reaching adesired threshold X corresponding a condition where 1:1 capture ispossible and is still suitable for valve deployment, such as a PPR ofaround 160 to around 180 beats per minute, or preferably at least 160beats per minute with adequate hypotension as determined by thecardiologist, for example. Once it is determined 812 that the PPR is atthe desired threshold, the valve may be deployed 1000 by thecardiologist. After successful valve deployment 1000, the pacing signalmay be dropped or ramped down 902 (e.g., to VVI 80 BPM) until it isdetermined 904 that pacing is inhibited, after which the operation canmove to the next stage (e.g., BP stage 900).

FIGS. 8-13 show detailed steps for using the system 100 according toexample embodiments. For purposes of explanation, not necessarilylimitation, the steps are organized according to the operational stagesmentioned above. Throughout FIGS. 8-13 , boxes shown in dashed lines aregenerally steps that may performed by the cardiologist, and boxes shownin solid lines are generally steps that may be at least partiallyperformed by executable code. The steps and processes are illustrated inflow diagrams, wherein the flow diagrams between pages are connected bycommon nodes (small black circles with letters).

FIG. 8 is a flow chart illustrating a start-up process 500 for using theEPG 200 and RCM 300, according to an example embodiment. To start 501,the EPG 200 may be powered on 505 by pressing the power button on theEPG 200. The RCM 300 may then be powered on 510 by actuating an on-offswitch on the back of the RCM (not visible) or by removal of aninsulated packing strip, for example, covering a battery terminal. TheEPG 200 and the RCM 300 may then be paired 515 by Bluetooth, forexample, to provide bidirectional wireless communication. The EPG 200may then execute a self-test 520 to check for faults in pairing,communication and other electrical faults. If faults are found, pairingmay be repeated. If no faults are found, the desired mode may beselected 530. As described previously, the four modes may include:bipolar pacing for a balloon expandable valve mode 532; bipolar pacingfor a self-expandable valve mode 534; unipolar pacing for aballoon-expandable valve mode 536; and unipolar pacing for aself-expandable valve mode 538. Generally speaking, the flow chartsshown in FIGS. 8-13 are with reference to bipolar balloon expandablemode 532, but the same processes may be used for the other modes 534,536 and 538 with modest modifications described hereinafter.

FIG. 9 is a flow chart illustrating a preparation process 540 accordingto an example embodiment. To start 541, the pacer (in the EPG 200) andthe background continuity test (described hereinafter) may be set tooff. The scrub nurse may prepare 544 the lead 20 according to standardpractice, plug a connector cable into the EPG 200 and attach 546 theguidewire connector 50 to the lead 20. The cable 52 may be connected 548to the EPG 200, and if operating in unipolar mode 536, 538, thegrounding pad 60 may be connected to the EPG 200 via cable 62. Theprocess may then proceed to the CT process 600 via node A.

FIG. 10A is a flow chart illustrating a CT process 600 according to anexample embodiment. The CT 600 may be broken down into two stages:continuity test 1 (CT1) wherein the process waits for the user to beready before verifying lead continuity; and continuity test 2 (CT2)wherein the continuity of the lead is verified over a period of time(e.g., several seconds). In CT1, the pacer and background continuitytest are initially set to off 610 and the continuity test indicator 220displays pretest status 612. Continuity is monitored and once found 614(suggesting the lead 20 is connected to the EPG 200 and the lead 20 isin a saline soak) the process may proceed to CT2 to confirm continuity.In CT2, the continuity test indicator 220 may display performing status616. Continuity is monitored for a period of time and if it isdetermined 618 the continuity is not lost after the period of timeexpires (timeout), the continuity test indicator 220 may displaycomplete status 620 and the accessory buttons 208 and 308 may bedisabled (unlit). The process may then proceed to CC 700 via node B.

However, if it is determined 618 that continuity has been lost, thecontinuity test indicator 220 may display failed status, and theaccessory buttons 208 and 308 may be enabled and lit 622. The processmay then wait for the accessory button 208 or 308 to be clicked to go tothe next step. Once it is determined 624 that the accessory button 208or 308 has been clicked, the process may return to CT1 to repeat thecontinuity test 600. At any time during the operational stages, if it isdetermined 630 that the primary button 206/306 and the accessory button208/308 have been long pressed at the same time, CT1 may be initiateddirectly at step 610.

FIG. 10B is a flow chart illustrating a back ground continuity test(BCT) process 640 according to an example embodiment. The BCT 640 mayrun continuously in the background unless specifically disabled. Forexample, in some instances, other processes may have an embeddedcontinuity test, the outcome of which may be unique to the process beingexecuted. If it is determined 642 that the BCT is enabled, continuity ismonitored and if it is determined 644 that continuity has been lost, thecontinuity test indicator 220 may display failed status 646. If it isdetermined 644 that continuity has not been lost, the continuity testindicator 220 may (continue to) display complete status 648.

FIGS. 11A-11D are flow charts illustrating a CC process 700 according toan example embodiment. The CC 700 process may be broken down into fourstages: capture check stage 1 (CC1) wherein the process waits untilcontinuity is confirmed and EGM is detected; capture check stage 2 (CC2)which automatically determines the appropriate PPR for capture check andautomatically ramps PPR; capture check stage 3 (CC3) which automaticallyverifies capture over at least one respiratory cycle; and capture checkstage 4 (CC4) which provides, in the alternative, allows for manuallyramping of PPR with user input.

With reference to FIG. 11A, CC1 may begin with the capture checkindicator 222 displaying pre-capture check status 722 and the primarybuttons 206 and 306 disabled (unlit). The cardiologist may then position698 the lead 20 in the desired position for pacing. A confirmatorycontinuity test may be performed and if it is determined 724 thatcontinuity has been lost, the process may return to step 722. If it isdetermined 724 that continuity has not been lost, EGM may be sensed 726,from which HR may be derived. If it is determined 228 that EGM is notdetected or not of sufficient amplitude, the process may return to step724, and the cardiologist may consider repositioning the lead 20 toobtain a better signal. If it is determined 728 that EMG is detected,the primary buttons 206 and 306 may be enabled and lit 730, and if it isdetermined 732 that the primary button 206 or 306 has been clicked, theprocess may proceed to CC2 via node C.

With reference to FIG. 11B, CC2 may begin with the capture checkindicator 222 displaying perform status 722. At any time during theoperational stages, if it is determined 790 that the accessory button208 or 308 has been long pressed, CC2 may be initiated directly. Theaccessory buttons 208 and 308 may then be lit 736 and the BCT may beturned on 738. The PPR may be set approximately 740 to approximately 115BPM in VVI pacing mode, with an amplitude of approximately 7 mA and apulse width of approximately 1.5 ms, for example. The pacer may beturned on 742 and the process may then execute a loop where the PPR isautomatically ramped up to approximately 150 BPM. This loop starts withdetermining 744 if the accessory button 208 or 308 has been clicked, andif so, exits the loop, turns off the alert 746, sets the PPR toapproximately 50 BPM and returns to step 734 to restart CC2. If theaccessory button 208 or 308 has not been clicked, a determination 748 ismade if pacing has been inhibited (i.e., HR>PPR). If pacing has not beeninhibited (i.e., PPR>HR, suggesting initial capture), the process exitsthe loop and enters CC3 (capture confirmation) via node H.

However, if pacing has been inhibited (i.e., HR>PPR), the PPR may beincreased by 10 BPM, for example, at step 750. A determination 752 maythen be made if the PPR is greater than approximately 150 BPM, forexample. If it is determined 752 that the PPR is less than approximately150 BPM, the loop repeats at step 744 to continue automatic ramping. Ifit is determined 752 that the PPR is greater than or equal toapproximately 150 BPM, the process exits the loop and enters CC4 (manualramping) via node E. This step may be described as a way to avoidcontinued automatic ramping when the PPR is above approximately 150 BPMwith inhibition, suggesting the HR>150 without initial capture, whichmay be a safety concern for the patient and warrants manual adjustmentof PPR in CC4.

With reference to FIG. 11C, manual ramping stage CC4, if needed, maybegin at 780 with the capture check indicator 222 displaying failedstatus, alert on, the primary buttons 206 and 306, the ancillary buttons208 and 308, the up 210, 310 and down 212, 312 buttons enabled and lit,and the PPR set to approximately 150 BPM. A determination 782 is made ifthe ancillary button 208 or 308 has been clicked. If so, the processreturns to step 746 via node G to reattempt automatic ramp in stage CC2.If not, a determination 784 is made if pacing is inhibited. If pacing isnot inhibited, the process may proceed directly to capture verificationin stage CC3 via node H. If pacing is inhibited, a determination is madeif the up 210/310 button or the down 212/312 button is clicked. Clicking787 the up button 210 or 310 may increase the PPR by approximately 10BPM, for example, up to a maximum of approximately 200 BPM, for example.Clicking 788 the down button 212 or 312 may decrease the PPR by 10 BPM,for example, down to a minimum of 30 BPM, for example. This allows thecardiologist to manually increase or decrease the PPR in an effort totroubleshoot lack of capture. If neither button is clicked or whenbutton clicking has stopped, the loop may be repeated by returning tostep 782 until pacing is no longer inhibited, and the process may thenproceed to capture verification in stage CC3 via node H.

With reference to FIG. 11D, CC3 (capture verification) may begin at step756 with the capture check indicator 222 displaying perform status,alerts off (if any), the accessory buttons 208 and 308 enabled and lit,the primary buttons 206 and 306 disabled and unlit, the up 210, 310 anddown 212, 312 buttons disabled and unlit, the respiratory time (RespT)set to zero, and the PPR being increased by approximately 10 BPM, forexample. The process may then enter a loop to automatically confirmcapture over a period of time corresponding to at least one respiratorycycle. This loop may start by determining 758 if the accessory button208 or 308 has been clicked, and if so, exiting the loop to return toCC2 via node G. Otherwise, a determination 760 is made if 1:1 capturehas been obtained. If 1:1 capture is not present, the capture checkindicator 222 displays failed status, the primary buttons 206 and 306are enabled and lit, and an alert is turned on at step 764. The processthen waits to determine 765 if the primary button 206 or 306 has beenclicked, and if so, the loop restarts at step 758 after the respiratorytime has been reset to zero at step 766. If capture is present, the loopcontinues at step 762 with the capture check indicator 222 displaying orcontinuing to display perform status, the primary buttons 206 and 306off and alerts off (if any). The respiratory time may then beincremented up an interval (p_intvl) corresponding to 1 second, forexample, at step 768. A determination 770 is made if the respiratorytime has reached the equivalent of 1 respiratory cycle (e.g.,approximately 8 seconds), and if not, the process repeats by checkingcapture 772 and incrementing the respiratory time 768. If the accessorybutton 208 or 308 is clicked 774 while the process is repeating, theloop is exited to return to CC2 via node G. Once capture has beenconfirmed for a period of time equivalent to at least one respiratorycycle, the PPR may be set to 50 BPM at step 776, the capture checkindicator 222 may display complete status at step 778, and the processmay proceed to the RP process via node D.

FIGS. 12A and 12B are flow charts illustrating a RP process 800according to an example embodiment. The RP process 800 may be brokendown into four stages: rapid pacing stage 1 (RP1) wherein the processwaits until the cardiologist is ready; rapid pacing stage 2 (RP2) whichautomatically ramps up PPR to a suitable level for valve deployment;rapid pacing stage 3 (RP3) wherein the cardiologist deploys the valve;and rapid pacing stage 4 (RP4) which automatically ramps down PPR in anattempt to regain capture if lost in RP2.

With reference to FIG. 12A, RP1 may begin at step 810 with the valvedeployment indicator 224 displaying pre-deployment status. Thecardiologist may then get the valve into position 1010 for deployment. Adetermination 812 may be made as to whether either the primary button206/306 or the accessory button 208/308 has been clicked. If it isdetermined 812 that the primary button 206 or 306 has been clicked,indicating the cardiologist is ready to continue, the process mayproceed to RP2. If it is determined 812 that the accessory button 208 or308 has been clicked, indicating the cardiologist wants to repeatcapture check, the process may return to CC2 via node F.

With continued reference to FIG. 12A, RP2 may begin at step 816 with thevalve deployment indicator 224 displaying perform status, and theaccessory buttons 208 and 308 enabled and lit. At any time during theoperational stages, if it is determined 890 that the primary button 206or 306 has been long pressed, RP2 may be initiated directly at step 816.At step 818, the PPR may then may then be set to 160 BPM in VVI modewith an amplitude of approximately 25 mA and a pulse width ofapproximately 1.5 ms, for example. The process may then enter a loopwhereby the PPR is automatically increased in increments ofapproximately 10 BPM, for example, until the PPR is equal to or greaterthan approximately 200 BPM, for example. Each cycle through the loopoffers the cardiologist the opportunity to exit to back-up pacing. Theloop may begin with a determination 820 as to whether the primary button206 or 306 has been clicked. If the primary button 206 or 306 has beenclicked, the BP process 900 may be initiated directly at via node J. Ifthe primary button 206 or 306 has not been clicked, a determination maybe made regarding capture. If 1:1 capture is not present, then theprocess may proceed to RP4 via node K. If 1:1 capture is present, adetermination 824 may be made as to whether the PPR has reachedapproximately 200 BPM or more. If the PPR is less than approximately 200BPM, the PPR may be increased by 10 BPM, for example, at step 826, andthe loop repeats. If the PPR is equal to or greater than approximately200 BPM, the valve deployment indicator 224 may display complete statusat step 828 and the process may proceed to RP3 via node I.

With reference to FIG. 12B, RP3 may begin at step 830 with the back-uppacing indicator 226 displaying pre-back-up pacing status. With thevalve deployment indicator 224 already displaying complete status, thecardiologist may then deploy the valve at step 1000. A determination 832may then be made as to whether the primary button 206 or 306 has beenclicked, indicating the valve deployment has been successful or at leastattempted, and the process may proceed to BP via node L.

With continued reference to FIG. 12B, RP4 may be entered in an attemptto regain capture lost in RP2 by reducing PPR, starting at step 834 withthe valve deployment indicator 224 displaying failed status. A loop maythen begin to automatically ramp down the PPR, check to see if capturehas been regained, and offer the cardiologist an opportunity to exit theloop to enter back-up pacing. The loop may be triggered automatically ormay be triggered in response to user input. The loop may begin byreducing the PPR by increments of 10 BPM, for example, at step 836. Adetermination 840 may then be made to see if the cardiologist hasclicked the primary button 206 or 306. If the primary button 206 or 306has been clicked, the loop may be exited to BP via node J. If theprimary button 206 or 306 has not been clicked, the loop continues bydetermining 842 if capture has been regained. If capture has not beenregained, the loop repeats ramping PPR down at step 836. If capture hasbeen regained, the valve deployment indicator 224 changes to completestatus, and the process may continue to RP3 for valve deployment.

FIG. 13 is a flow chart illustrating a BP process 900 according to anexample embodiment, wherein the PPR is automatically ramped down untilintrinsic pacing is established. BP may start at step 910 where theback-up pacing indicator 226 displays perform status. The PPR may thenbe set to approximately 80 BPM, VVI mode, with an amplitude ofapproximately 25 mA and a pulse width of approximately 1.5 ms, forexample, in step 912. A determination 912 may then be made to assesswhether the pacer is inhibited, suggesting, in VVI mode, that the HR>PPRand that intrinsic pacing has been established. If pacing has not beeninhibited, the PPR may be ramped down to approximately 50 BPM overapproximately 10 seconds, for example at step 916, periodicallydetermining 914 if pacing has been inhibited. If pacing has beeninhibited, the back-up pacing indicator 226 displays complete status,and the PPR may be set to approximately 50 BPM, for example, or turnedoff after a period of time. If pacing has not been inhibited atapproximately 40-50 BMP, an alarm may be triggered indicating that thepatient may be experiencing pathologic bradycardia and the process mayenter a manual state where the PPR starts at 50 BPM in VVI mode and theup and down buttons may be used for manual pacing control to return tonormal HR. At this point, the stages are complete, suggesting an end tothe TAVR procedure, but any stage may be restarted as desired.

The bipolar pacing of a self-expandable valve mode 534 may involve thesame or similar to steps involved in mode 532 with the followingexceptions. When initiated by the RCM 300, the EPG 200 may pace atapproximately 25 mA, approximately 1.5 ms pulse width, and a PPR ofapproximately 120 BPM, for example. If PVCs are detected, the EPG 200may increment PPR by 15 BPM every 500 ms seconds until there are no PVCsor the HR reaches 150 BPM. This may be accomplished automatically by thealgorithm or triggered by pressing the up button 310 on the RCM 300.

The unipolar pacing of a balloon-expandable valve mode 536, and theunipolar pacing of a self-expandable valve mode 538 may involve the sameor similar to steps involved in mode 532 with the following exceptions.When a grounding pad 60 is plugged into EPG 200, the EPG 200 mayreconfigure the outputs such that the anode signal is connected to bothoutputs to the lead 20 and the cathode signal is connected to thegrounding pad 60. The grounding pad 60 may be placed over the apex ofthe heart on the chest wall, for example. The same steps may be executedbut CC may be run at 12 mA and 1.5 ms pulse width.

According to embodiments of the disclosed subject matter, an EPG (e.g.,EPG 200) described herein may be used for temporary or single-use pacingin clinical settings outside an interventional lab. Such settings mayinclude, but are not limited to, post cardiac surgery settings withsurgically placed leads, or in an emergency department or intensive careunit (ICU) for single chamber temporary leads (e.g., right ventricle(RV) leads). Alternatively, or in addition, an EPG disclosed herein maybe used for percutaneous pacing for acute heart block, for example,based on a superficial sensing algorithm. Traditional EPGs do not applyintelligence with respect to sensing and/or pacing. An EPG disclosedherein may be implemented using smart pacing functionality to augment auser experience of temporary or single-use pacing outside aninterventional lab, and may be used without an RCM (e.g., RCM 300). AnEPG disclosed herein may be configured to include one or more inputs andone or more outputs for connection to an ECG lead cable for connectionto a plurality (e.g., five) of leads. Such a configuration may providethe capacity for capture detection and pacing (e.g., two outputs toconnect to a pacing lead for both atrial and ventricular leads). Such anEPG may have minimal controls for simplicity, and may include a paceron/off toggle, manual override heartrate up and down controls, and/or adisplay for displaying a pacing rate.

According to embodiments of the disclosed subject matter, an EPG (e.g.,EPG 200) described herein may sense ECG and/or EGM signals and maydetect fiducials of a Q wave, R wave, and S wave (QRS) complex such asdetection of an R wave. An EPG disclosed herein may also indicate, forexample, on a display, a set sensing threshold (e.g., a sensing setting)and may indicate a margin above the sensing threshold. The sensingthreshold may include or may be based on an auto sense feature to managethe risk of over sensing and/or under sensing. Such a risk may bemanaged, for example, as the signal to noise ratio changes in a moresubacute implantation of a temporary or single-use lead. Such a risk maybe present, for example, over a range of time (e.g., hours or days).Sensing detection disclosed herein may be implemented continuously.Based on the continuous sensing, one or more metrics may be generated.For example, a metric based on an R wave height, or A wave height withrespect to the atrial channel, may be plotted over time. Alternatively,or in addition, if a lead has access to multiple bipoles (e.g., based onmultiple connections), the EPG may apply an algorithm (e.g., using code,as disclosed herein) to simultaneously assess all or a plurality of thebipoles and to select the bipoles with the highest measured R or A wavesor those above a threshold, with the lowest signal to noise ratio or asignal to noise ration below a threshold. Such selected bipoles may beused for sensing and pacing. All or a plurality of the bipoles may beassessed periodically, or when there is a substantive change in R or Awave height, to select a different bipole. Changes in tissue contact orlead fibrosis may trigger different bipoles being selected over time.Such selection to shift sensing and pacing sites may optimize pacemakerfunction.

According to embodiments of the disclosed subject matter, an EPG (e.g.,EPG 200) described herein may perform a pacing threshold test (e.g.,percutaneous capture or EGM capture) to determine the quality of pacingand lead contact. An EPG disclosed herein may indicate, for example, ona display, an indication or the results of the last performed pacingthreshold test and may also indicate one or more current leadthresholds. The pacing threshold test may be performed automatically onbased on a schedule (e.g., a scheduled defined by a user). According toan embodiment, alert levels may be set (e.g., defined by a user), wherethe alert levels are based on pacing threshold that defines failure inisolation. Alternatively, or in addition, a pacing threshold may betracked over time, and an increase in pacing threshold (e.g., by apre-set value or percentage) may be used to alert a user of a potentialimpending problem with a lead position.

Embodiments disclosed herein include:

1. A system for assisted pacing during a transcatheter heart valvereplacement (TAVR) procedure, wherein a heart valve is deployed in aheart paced via a lead positioned in the heart, the system comprising:

an external pulse generator (EPG) configured for connection to the lead;and

a remote-control module (RCM) wirelessly connected to the EPG, whereinthe RCM includes user inputs configured to control the EPG.

2. A system as in embodiment 1, wherein the lead comprises a guidewirewith at least a partial insulative outer portion, the system furtherincluding a guidewire connector connected to the EPG via a cable, theguidewire connector configured to penetrate the insulative outer portionto establish electrical communication with the guidewire.

3. A system as in embodiment 1, further comprising:

a central processing unit (CPU) with a memory unit for storing code anda processor for executing the code, wherein the CPU is operablyconnected to the EPG and RCM;

wherein the code includes instructions to control the EPG based on userinput from the RCM.

4. A system as in embodiment 3, wherein the CPU is disposed in the EPG.

5. A system as in embodiment 3, wherein the CPU is disposed in the RCM.

6. A system as in embodiment 3, further comprising an interface module(IM) to facilitate communication between the EPG and RCM.

7. A system as in embodiment 6, wherein the CPU is disposed in the IM.

8. A system as in embodiment 3, wherein the code includes instructionsto perform a rapid pacing (RP) routine based on user input from the RCM.

9. A system as in embodiment 8, wherein the RP routine includes thesteps of waiting for a user readiness input from the RCM, ramping up apaced pulse rate (PPR) of a pacing output from the EPG, and triggeringan indicator when the PPR is suitable for valve deployment.

10. A system as in embodiment 9, wherein the RP routine further includesan automatic PPR ramp up subroutine and an automatic ramp downsubroutine.

11. A system as in embodiment 8, wherein the code further includesinstructions to perform a continuity test (CT) routine based on userinput from the RCM.

12. A system as in embodiment 11, wherein the code further includesinstructions to perform a capture check (CC) routine based on user inputfrom the RCM.

13. A system as in embodiment 12, wherein the CC routine includes thesteps of waiting for a user readiness input from the RCM, ramping up apacing output from the EPG, determining if a sensed heart-rate (HR) isthe same as the PPR, and triggering an indicator indicative of 1:1capture.

14. A system as in embodiment 13, wherein the CC routine furtherincludes an automatic rate determination subroutine.

15. A system as in embodiment 13, wherein the CC routine furtherincludes a manual capture rate determination subroutine.

16. A system as in embodiment 13, wherein the CC routine furtherincludes a capture verification subroutine.

17. A system as in embodiment 16, wherein the capture verificationsubroutine monitors capture over a period corresponding to at least onerespiratory cycle.

18. A system as in embodiment 12, wherein the code further includesinstructions to perform a back-up pacing (BP) routine based on userinput from the RCM.

19. A system as in embodiment 18, wherein the BP routine includes thesteps of waiting for a user readiness input from the RCM, ramping down apacing output from the EPG, determining if a heart-rate (HR) isinhibited, and triggering an indicator indicative of inhibition.

20. A method of temporary cardiac pacing during a transcatheter heartvalve replacement (TAVR) procedure wherein a heart valve is deployed viaa guidewire, the method comprising:

connecting an external pulse generator (EPG) to the guidewire;

connecting a remote-control module (RCM) to the EPG;

activating a computer executable code based on a user input from theRCM; and

executing code instructions to perform a rapid pacing (RP) routine basedon the user input from the RCM.

21. A method as in embodiment 20, wherein executing the instructions toperform the RP routine includes the steps of waiting for a userreadiness input from the RCM, ramping up a paced pulse rate (PPR) of apacing output from the EPG, and triggering an indicator when the PPR issuitable for valve deployment.

22. A method as in embodiment 21, wherein executing the instructions toperform the RP routine includes the step of automatically ramping upPPR.

23. A method as in embodiment 22, wherein executing the instructions toperform the RP routine includes the step of automatically ramping downPPR.

24. A method as in embodiment 21, further comprising executing codeinstructions to perform a continuity test (CT) routine based on userinput from the RCM.

25. A method as in embodiment 24, further comprising executing codeinstructions to perform a capture check (CC) routine based on user inputfrom the RCM.

26. A method as in embodiment 25, wherein executing the instructions toperform the CC routine includes the steps of waiting for a userreadiness input from the RCM, ramping up the PPR of the pacing outputfrom the EPG, determining if a sensed heart-rate (HR) is the same as thepacing output, and triggering an indicator indicative of 1:1 capture.

27. A method as in embodiment 26, wherein executing the instructions toperform the CC routine includes the step of automatically determiningcapture rate.

28. A method as in embodiment 26, wherein executing the instructions toperform the CC routine includes the step of manually determining capturerate.

29. A method as in embodiment 26, wherein executing the instructions toperform the CC routine includes the step verifying 1:1 capture.

30. A method as in embodiment 29, wherein the step of verifying captureis performed over a period corresponding to at least one respiratorycycle.

31. A method as in embodiment 25, further comprising executing codeinstructions to perform a back-up pacing (BP) routine based on userinput from the RCM.

32. A method as in embodiment 31, wherein executing the instructions toperform the BP routine includes the steps of waiting for a userreadiness input from the RCM, ramping down the PPR of the pacing outputfrom the EPG, determining if a heart-rate (HR) is inhibited, andtriggering an indicator indicative of inhibition.

All of the aspects described in the present disclosure (includingreferences incorporated by reference, accompanying claims, abstract anddrawings), may be combined in any order, in part or in full, or in anycombination or modification, except when such are incompatible orinconsistent. Furthermore, each aspect may be replaced by alternativefeatures serving the same, equivalent or similar purpose, unlessexpressly stated otherwise or inconsistent with the teachings herein.Thus, unless expressly stated otherwise, each aspect disclosed hereinmay be only an example of equivalent or similar features. It is intendedthat the invention be defined by the attached claims and their legalequivalents.

What is claimed is:
 1. A system for cardiac pacing, the systemcomprising: an external pulse generator (EPG) configured to connect toan intracardiac lead and to provide pacing outputs; and a centralprocessing unit (CPU) operably connected to the EPG, the CPU includingcode having instructions, wherein the CPU is configured to execute thecode to perform a rapid pacing (RP) routine, the RP routine comprising:modifying a paced pulse rate (PPR) of a first pacing output to generatea second pacing output, of the pacing outputs; in response to generatingthe second pacing output, sensing a cardiac electrical signal ofintracardiac tissue; further in response to generating the second pacingoutput, automatically determining if a PPR of the second pacing outputmeets a predetermined setting for elevating a heart rate (HR) to anelevated HR above an intrinsic HR based on the sensed cardiac electricalsignal; generating a first indicator indicating that the modified PPRmeets the predetermined setting, when the modified PPR is determined tomeet the predetermined setting; and modifying the PPR of the secondpacing output to generate a third pacing output, of the pacing outputs,wherein a PPR of the third pacing output is lower than the PPR of thesecond pacing output.
 2. The system of claim 1, wherein the sensedelectrical signal is one of an electrocardiogram (ECG) signal or anelectrogram (EGM) signal.
 3. The system of claim 1, wherein the CPU isfurther configured to execute the code to perform a continuity test (CT)routine, the CT routine comprising: determining that the intracardiaclead is connected to the EPG; and generating a second indicatorindicating that the intracardiac lead is connected to the EPG, when theintracardiac lead is determined to be connected to the EPG.
 4. Thesystem of claim 3, wherein the EPG comprise one or more accessorybuttons, the CT routine further comprising disabling the one or moreaccessory buttons in response to determining that the intracardiac leadis connected to the EPG.
 5. The system of claim 1, wherein the RProutine further comprises: in response to automatically determining ifthe PPR of the second pacing output meets the predetermined setting forelevating the HR to the elevated HR, automatically maintaining thesecond pacing output.
 6. The system of claim 1, wherein the RP routinefurther comprises: in response to automatically determining if the PPRof the second pacing output meets the predetermined setting forelevating the HR to the elevated HR, automatically maintaining thesecond pacing output, and wherein the second pacing output isautomatically maintained to allow completion of a cardiac intervention.7. The system of claim 1, wherein modifying the PPR of the first pacingoutput to generate a second pacing output is based on an automatic PPRramp up subroutine.
 8. The system of claim 1, wherein the system furthercomprises a guidewire connector connected to the EPG, the guidewireconnector being configured to penetrate a partial insulative outerportion of the intracardiac lead to establish electrical communicationwith a guidewire of the intracardiac lead.
 9. The system of claim 1,wherein the CPU is further configured to execute the code to perform acapture check (CC) routine, the CC routine comprising: ramping up thePPR of the first pacing output to a ramped up PPR; receiving a sensedHR; determining if the sensed HR is approximately the same as the rampedup PPR; and generating a second indicator, the second indicatorindicative of a 1:1 capture in response to determining if the sensed HRis approximately the same as the ramped up PPR.
 10. The system of claim9, wherein the CC routine further includes an automatic ratedetermination subroutine.
 11. The system of claim 9, wherein the CCroutine further includes at least one of a manual capture ratedetermination subroutine or a capture verification subroutine.
 12. Thesystem of claim 11, wherein the capture verification subroutine monitorscapture over a period of at least one respiratory cycle.
 13. The systemof claim 1, wherein the CPU is further configured to execute the code toperform a back-up pacing (BP) routine, the BP routine comprising: inresponse to modifying the PPR of the second pacing output to generate athird pacing output, determining if an HR is inhibited; and generating asecond indicator indicative of inhibition in response to determining ifthe HR is inhibited.